+++ This bug was initially created as a clone of Bug #1425726 +++ Description of problem: Stale export entries in ganesha.conf in shared storage after executing "gluster nfs-ganesha disable" Version-Release number of selected component (if applicable): glusterfs-3.8.4-14 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: stale entries in ganesha.conf Expected results: entries should be removed Additional info: --- Additional comment from Worker Ant on 2017-02-22 04:07:54 EST --- REVIEW: https://review.gluster.org/16708 (ganesha/scripts : Remove export entries from ganesha.conf during cleanup) posted (#1) for review on release-3.10 by jiffin tony Thottan (jthottan)
Verified as follows: Execute gluster nfs-ganesha disable and check the /etc/ganesha/ganesha.conf file for any stale export entries. Verified that there are no stale export entries in ganesha.conf and then gluster nfs-ganesha enable works fine. Version: nfs-ganesha-2.4.4-4.el7rhgs.x86_64 glusterfs-ganesha-3.8.4-24.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.4-4.el7rhgs.x86_64 Moving the BZ verified.
Looks good to me
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774